First of all, during Scan, we cannot know the unit of the return value. For example, the units of TTL and PTTL are different. In addition, for the value set by the user, we cannot take it for granted that it is nanoseconds (time.Duration(n) ).

In the writeArg command, we will not write the time.Duration type, because there is no time.Duration in redis, it is just the type of go.

I guess this is for Set and Get

rdb.Set(ctx, "foo", time.Second, 0)

var d time.Duration
rdb.Get(ctx, "foo").Scan(&d)

// or

rdb.Get(ctx, "foo").Duration()

Probably this is fine, but @Pyrodash please add a test and change commit to follow https://www.conventionalcommits.org/en/

Fixes #1929

I guess this is for Set and Get

rdb.Set(ctx, "foo", time.Second, 0)

var d time.Duration
rdb.Get(ctx, "foo").Scan(&d)

// or

rdb.Get(ctx, "foo").Duration()

Probably this is fine, but @Pyrodash please add a test and change commit to follow https://www.conventionalcommits.org/en/

Yes, this is my intended use case.
I've added a test case, the commit is passing the linter so I think it's fine?

Thanks